Artifact: Development Case

Development Case	The development-case description describes the development process that you have chosen to follow in your project.
Worker:	Process Engineer
Enclosed in:	Software Development Plan
Template:	Microsoft Word Template HTML Template
More Information:	Development Case Important Decisions in Business Modeling Important Decisions in Requirements Important Decisions in Analysis & Design Important Decisions in Implementation Important Decisions in Test Important Decisions in Deployment Important Decisions in Environment Important Decisions in Project Management Important Decisions in Configuration & Change Management Process Discriminants RUP Style The File Structure of RUP Classifying Artifacts Review Levels
Examples:	Development Case Course Registration System Collegiate Sports Paging System (e-Business)
Purpose Brief Outline Timing Responsibility Tailoring Annotated Outline (hyperlinks into HTML template in a new window) Additional Information

Input to Activities: Acquire Staff Compile Software Development Plan Develop Business-Modeling Guidelines Develop Design Guidelines Develop Development Case Develop Iteration Plan Develop Manual Styleguide Develop Programming Guidelines Develop Project-Specific Templates Develop Test Guidelines Develop Tool Guidelines Develop Use-Case Modeling Guidelines Develop User-Interface Guidelines Launch Development Case Select & Acquire Tools Set Up Tools Verify Tool Configuration and Installation

Output from Activities: Develop Development Case

Purpose

The purpose of the Development Case is to capture the tailored process for the individual project.

Brief Outline

(hyperlinks into HTML template in a new window)

• Introduction
  • Purpose
  • Scope
  • Definitions, Acronyms and Abbreviations
  • References
  • Overview
• Overview of the Development Case
  • Lifecycle Model
  • Core Workflows
  • Core Workflow Configuration
  • Artifact Classification
  • Review Procedures
  • Sample Iteration Plans
• Core Workflows
  • Business Modeling
  • Requirements
  • Analysis & Design
  • Implementation
  • Testing
  • Deployment
  • Configuration & Change Management
  • Project Management
  • Environment
• Workers 

Timing

The Development Case is created in the early Inception Phase, and is updated throughout the project as needed.

A first version of the development case is created at the onset of the project. It is recommended to develop the development case in increments, covering more and more of the core process workflows in each iteration. The first version of the development case will normally only cover a subset of the core process workflows. In each of the subsequent iterations, more will be covered by the development case. As you evaluate the results of each iteration the development case is likely to change based on the lessons learned.

Responsibility

The Worker: Process Engineer is responsible for creating and maintaining the Development Case.

Tailoring

Normally, a project do not start using all workflows in the Rational Unified Process. In that case the corresponding sections can be removed.

If needed, add more information about how to use the artifacts for each core process workflow. For example, add references to templates used to describe the artifacts.

If needed, add references to guidelines and information that the project wants to use in addition to the Rational Unified Process.

Additional Information

Use the development case in parallel with the Iteration Plan for each iteration. The development case tells specifically what parts of each model you have chosen to use in your project.

Copyright  ⌐ 1987 - 2000 Rational Software Corporation

Rational Unified Process